METHODS, SYSTEMS, AND COMPUTER READABLE MEDIA FOR RESOURCE OPTIMIZATION IN GROUP MESSAGE DELIVERY FOR NARROWBAND INTERNET OF THINGS (NB-IoT) DEVICES

ABSTRACT

According to one aspect, the subject matter described herein includes a method for service-specific group message delivery to narrowband Internet of things (IoT) devices. The method includes operations performed by a network node including at least one processor. The operations include receiving, on a first interface, a request for service-specific group message delivery to narrowband IoT devices supporting a specified service. The operations further include generating, by the network node, a message for service-specific group message delivery for transmission on a second interface, the message including a NB-IoT service information parameter for identifying a narrowband IoT service provided by the narrowband IoT devices supporting the specified service. The operations further include transmitting, from the network node and on the second interface the message for service-specific group message delivery to narrowband IoT devices.

TECHNICAL FIELD

The subject matter described herein relates to routing messages to IoTdevices. More particularly, the subject matter described herein relatesto methods, systems, and computer readable media for resourceoptimization in group message delivery to narrowband IoT devices.

BACKGROUND

Narrowband IoT is a low power wide area network (LP WAN) radiotechnology standard developed by the 3^(rd) Generation PartnershipProject (3GPP). Narrowband IoT enables an IoT device to have extendedbattery life, as the frequency of data transmission is on the order ofhours or days, depending on the service supported by the device. Thedevice can remain in a sleep mode between transmissions to conservebattery life.

The node in the narrowband IoT network that instructs narrowband IoTdevices to wake up and deliver messages is called the IoT applicationserver or AS. The IoT application server or AS in the network maysupport multiple services. To initiate communications with narrowbandIoT devices in a network, the IoT AS may initiate group message deliverywith all of the narrowband IoT devices in the network. The group messagedelivery is effected by sending a paging request to all of the devices,regardless of whether the devices support the service that is ofinterest to the AS. The result of the paging message is to wake up allof the IoT devices in the network, including those that do not supportthe service in which the AS is interested. Waking up devices that do notsupport a given service results in unnecessary power consumption andreduced battery life. In addition, signaling bandwidth in the networkcan be unnecessarily consumed when devices that do not support a givenservice respond to a group message.

3GPP specifications do not support a mechanism to only page a UE thatsupports a specific service. 3GPP specifications also do not define amechanism for an IoT device to avoid establishing a radio connection inresponse to paging for a group message delivery procedure. Accordingly,in light of these difficulties, there exists a need for improvedmethods, systems, and computer readable media for resource optimizationin group message delivery to narrowband IoT devices.

SUMMARY

The subject matter described herein introduces service awareness inpaging for IoT devices during the scenario of group message delivery toavoid the devices being awakened when they do not support a givenservice. Supporting service awareness requires modification of manynodes and interfaces in the network over what is currently specified by3GPP standards. For example, the T8 interface is the interface used bythe service capability server/application server (SCS/AS) to registernew IoT devices and to request information from registered IoT devices.On this interface, the group message delivery procedure between theSCS/AS and the network exposure function/service capability exposurefunction (NEF/SCEF) is modified to include service information for whichthe group message delivery procedure is applicable. For example, themessage from the SCS/AS to initiate the group message delivery proceduremay specify service 1, service 2, or service n when requesting groupmessage delivery.

Another modification that may be made is that the home subscriberserver/user data management node (HSS/UDM) may be modified to validateservice information for a narrowband IoT device. For example, when anIoT device is onboarded onto the network, the HSS/UDM may authorize thedevice and the service identifier that identifies the service providedby the device.

Yet another interface that may be modified is the T6a interface betweenthe NEF/SCEF and the access management function/mobility managemententity (AMF/MME). The procedure used to initiate a paging request ortransmission of other data to NB IoT devices on the T6a interface isreferred to as the mobile terminated non-IP data delivery (MT-NIDD)procedure. According to the subject matter described herein, the MT-NIDDprocedure will be modified to include service information identifyingthe service for which paging or other communication is requested. Thus,the NEF and/or SCEF may be modified or configured to include a serviceidentifying parameter in the message transmitted to the AMF or MME onthe T6a interface for group message delivery to narrowband IoT devices,the AMF or MME may be configured to decode the service identifyingparameter and formulate a corresponding message for effecting groupmessage delivery to IoT devices.

Yet another interface that is modified is the S1-AP interface betweenthe AMF/MME and the g-nodeB/e-nodeB (gNB/eNB). On the S1-AP interface,the paging procedure towards the gNB/eNB is modified to include serviceinformation. For example, the AMF or MME may include the serviceidentifying parameter in messages to the gNB or eNB for group messagedelivery to NB-IoT devices.

Yet another interface that requires modification to supportservice-specific paging is the interface between the gNB/eNB and the IoTdevices. The paging message sent from the gNB/eNB towards the IoTdevices will include service identifying parameters. It is important tonote that the paging message may be received by NB-IoT devices thatsupport the service identified by the service identifying parameter andby NB-IoT devices that do not support the service identified by theservice identifying parameter.

The IoT devices may also be modified to support identification of aservice in an MT-NIDD message. The IoT devices may be modified such thatcompliant devices only respond to MT-NIDD messages that identify aservice that is supported by the receiving NB-IoT devices. NB-IoTdevices that support the service identified in the MT-NIDD message mayrespond to the requesting eNB-gNB according to the service. For example,if the NB-IoT devices are sensors, the devices may respond to themessage with sensor data. If the NB-IoT devices do not support theidentified service, the NB-IoT devices may refrain from waking up andresponding to the message from the eNB or gNB.

According to one aspect, the subject matter described herein includes amethod for service-specific group message delivery to narrowbandInternet of things (IoT) devices. The method includes operationsperformed by a network node including at least one processor. Theoperations include receiving, on a first interface, a request forservice-specific group message delivery to narrowband IoT devicessupporting a specified service. The operations further includegenerating, by the network node, a message for service-specific groupmessage delivery for transmission on a second interface, the messageincluding a NB-IoT service information parameter for identifying anarrowband IoT service provided by the narrowband IoT devices supportingthe specified service. The operations further include transmitting, fromthe network node and on the second interface the message forservice-specific group message delivery to narrowband IoT devices.

According to another aspect of the subject matter described herein, thenetwork node comprises a service capability exposure function (SCEF),the first interface comprises a T8 interface, and the second interfacecomprises an S6a interface.

According to yet another aspect of the subject matter described herein,the network node comprises a network exposure function (NEF), the firstinterface comprises a T8 interface, and the second interface comprisesan Nudm interface.

According to yet another aspect of the subject matter described herein,the network node comprises a short message service center (SMS-SC).

According to yet another aspect of the subject matter described herein,the network node comprises a mobility management entity (MME), the firstinterface comprises an S6a interface, and the second interface comprisesan S1AP interface.

According to yet another aspect of the subject matter described herein,the network node comprises an access management function (AMF), thefirst interface comprises an Nudm interface, and the second interfacecomprises an N2 interface.

According to yet another aspect of the subject matter described herein,the network node comprises an evolved node B (eNB), the first interfacecomprises an S1AP interface, and the second interface comprises a radioresource control (RRC) interface.

According to yet another aspect of the subject matter described herein,the network node comprises a g-node B (gNB), the first interfacecomprises an N2 interface, and the second interface comprises a radioresource control (RRC) interface.

According to yet another aspect of the subject matter described herein,the message comprises a paging message.

According to yet another aspect of the subject matter described herein,the method further includes receiving, by a narrowband IoT device, themessage for service-specific narrowband IoT group message delivery. Themethod further includes determining, by the narrowband IoT device,whether the service identified by the NB-IoT service informationparameter corresponds to a service provided by the narrowband IoTdevice. The method further includes, in response to determining that theservice identified by the NB IoT device service identifier correspondsto a service provided by the narrowband IoT device, initiating wake-upof the narrowband IoT device. The method further includes, in responseto determining that the service identified by the NB IoT device serviceidentifier is not a service provided by the narrowband IoT device,ignoring the message and refraining from initiating wake up of thenarrowband IoT device.

According to yet another aspect of the subject matter described herein,a system for service-specific group message delivery to narrowbandInternet of things (IoT) devices is provided. The system includes anetwork node including at least one processor. The network node furtherincludes a first interface for receiving a request for service-specificgroup message delivery to narrowband IoT devices supporting a specifiedservice. The network node further includes a service-specific groupmessage narrowband IoT message generator implemented by the at least oneprocessor for generating a message for service-specific group messagedelivery to narrowband IoT devices, the message including a NB-IoTservice information parameter for identifying a narrowband IoT serviceprovided by the narrowband IoT devices supporting the specified service.The network node further includes a second interface for transmittingthe message for service-specific group message delivery to narrowbandIoT devices.

According to yet another aspect of the subject matter described herein,the network node comprises a service capability exposure function(SCEF), the first interface comprises a T8 interface, and the secondinterface comprises an S6a interface.

According to yet another aspect of the subject matter described herein,the network node comprises a network exposure function (NEF), the firstinterface comprises a T8 interface, and the second interface comprisesan Nudm interface.

According to yet another aspect of the subject matter described herein,the network node comprises a short message service center (SMS-SC).

According to yet another aspect of the subject matter described herein,the network node comprises a mobility management entity (MME), the firstinterface comprises an S6a interface, and the second interface comprisesan S1AP interface.

According to yet another aspect of the subject matter described herein,the network node comprises an access management function (AMF), thefirst interface comprises an Nudm interface and the second interfacecomprises an N2 interface.

According to yet another aspect of the subject matter described herein,the network node comprises an evolved node B, the first interfacecomprises an S1AP interface, and the second interface comprises a radioresource control (RRC) interface.

According to yet another aspect of the subject matter described herein,the network node comprises a g-node B (gNB), the first interfacecomprises an N2 interface, and the second interface comprises a radioresource control (RRC) interface.

According to yet another aspect of the subject matter described herein,the system includes a narrowband IoT device for receiving, the messagefor service-specific narrowband IoT group message delivery, determining,whether the service identified by the NB IoT device service identifiercorresponds to a service provided by the narrowband IoT device, inresponse to determining that the service identified by the NB IoT deviceservice identifier corresponds to a service provided by the narrowbandIoT device, initiating wake-up of the narrowband IoT device, and, inresponse to determining that the service identified by the NB IoT deviceservice identifier is not a service provided by the narrowband IoTdevice, ignoring the message and refraining from initiating wake up ofthe narrowband IoT device.

According to yet another aspect of the subject matter described herein anon-transitory computer readable medium having stored thereon executableinstructions that when executed by the processor of a computer controlthe computer to perform steps is provided. The steps are performed at anetwork node including at least one processor. The steps includereceiving, on a first interface, a request for service-specific groupmessage delivery to narrowband IoT devices supporting a specifiedservice. The steps further include generating, by the network node, amessage for service-specific group message delivery for transmission ona second interface, the message including a NB-IoT service informationparameter for identifying a narrowband IoT service provided by thenarrowband IoT devices supporting the specified service. The stepsfurther include transmitting, from the network node and on the secondinterface the message for service-specific group message delivery tonarrowband IoT devices.

The subject matter described herein can be implemented in software incombination with hardware and/or firmware. For example, the subjectmatter described herein can be implemented in software executed by aprocessor. In one exemplary implementation, the subject matter describedherein can be implemented using a non-transitory computer readablemedium having stored thereon computer executable instructions that whenexecuted by the processor of a computer control the computer to performsteps. Exemplary computer readable media suitable for implementing thesubject matter described herein include non-transitory computer-readablemedia, such as disk memory devices, chip memory devices, programmablelogic devices, and application specific integrated circuits. Inaddition, a computer readable medium that implements the subject matterdescribed herein may be located on a single device or computing platformor may be distributed across multiple devices or computing platforms.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a message flow diagram illustrating exemplary messages forservice-specific IoT device onboarding;

FIG. 2 is a message flow diagram illustrating service-specific groupmessage delivery for narrowband IoT devices;

FIG. 3 is a message flow diagram illustrating service-specificnon-access stratum (NAS) data delivery to a narrowband IoT device inidle mode;

FIG. 4 is a block diagram illustrating an exemplary network node forservice-specific group message delivery to narrowband IoT devices;

FIG. 5 is a block diagram illustrating an exemplary NB-IoT devicesupporting service-specific group message delivery;

FIG. 6 is a flow chart illustrating an exemplary process performed by anetwork node in supporting service-specific group message delivery toNB-IoT device; and

FIG. 7 is a flow chart illustrating an exemplary process performed by anNB-IoT device in supporting service-specific group message delivery.

DETAILED DESCRIPTION

Prior to initiating group message delivery to narrowband IoT devices,the IoT devices may be onboarded or registered with the network alongwith services supported by the narrowband IoT devices. FIG. 1 is amessage flow diagram illustrating IoT device onboarding with supportedservices.

Referring to FIG. 1, in line 1, SCS/AS 100 sends an NIDD configurationrequest message on the T8 interface to NEF/SCEF 102. The NIDDconfiguration request includes the external ID of the IoT device and anew parameter, NB-IoT-service-info, identifying the service supported bythe device. In line 2, NEF/SCEF 102 receives the onboarding requestincluding the external ID and the service identifier. In line 3,NEF/SCEF 102 sends a non-IP data delivery information request (NIR)message on the S6t interface to UDM/HSS 104. The NIR message includesthe external ID of the IoT device and the service identifier.

In line 4 of the message flow diagram, UDM/HSS 104 authorizes theonboarded IoT device and service identifiers. In line 5, UDM/HSS 104sends a non-IP data delivery information answer message to NEF/SCEF 102indicating that the IoT device and the requested service have beenvalidated. In response to receiving notification of the successfulvalidation, NEF/SCEF 102 creates a mapping between the external ID andthe service identifier.

In line 6 of the message flow diagram, NEF/SCEF 102 sends an NIDDconfiguration response message on the T8 interface to SCS/AS 100indicating successful configuration of the NB-IoT device. In line 7 ofthe message flow diagram, NEF/SCEF 102 stores a mapping between MCreceived in the NIA message and the NIDD information, including theservice identifier. After line 7, the NIDD service configuration iscomplete.

Once an NB-IoT device has been registered with the network, and each ofthe nodes have been modified to support service identification as partof a group message delivery procedure, an SCS/AS can initiate aservice-specific group message delivery to NB-IoT devices in thenetwork, and only those devices that are configured to support thespecified service will respond to the group message delivery procedure.FIG. 2 is a message flow diagram illustrating service-specific groupmessage delivery. Referring to FIG. 2, in line 1 of the message flowdiagram, SCS/AS 100 initiates a service-specific group message deliveryprocedure by sending an MT NIDD submit request message to NEF/SCEF 102on the T8 interface. The MT NIDD submit request message includes anexternal group ID that identifies NB-IoT devices, an external ID, amobile subscriber integrated services digital network (MSISDN) number,and the NB-IoT-service-info parameter, which identifies the specificservice.

In line 2, NEF/SCEF 102 receives the MT NIDD submit request message,authorizes the SCS/AS, and resolves the international mobile subscriberidentifiers (IMSISs). The external group ID is resolved to external IDsof individual UEs. In step 2B, NEF/SCEF 102 sends an MT NIDD submitresponse message to SCS/AS 100. The submit response message indicatesthat the submit request was successfully received and authorized.

In line 3 of the message flow diagram, NEF/SCEF 102 sends an NIDD submitrequest message on the T6a interface to MME/AMF 106. The NIDD submitrequest includes the IMSI and the NB-IoT-service-info parameter, whichidentifies the requested service. The purpose of the NIDD submit requestis for NEF/SCEF 102 to execute NIDD delivery per IMSI to all IoT devicesthat support a specific service. If the IoT devices are unreachable,MME/AMF 106 in step 4 responds with an NIDD submit response message toNEF/SCEF 102 indicating that the IoT devices are unreachable. In line 5,NEF/SCEF 102 sends an MT NIDD submit response to SCS/AS 100 indicatingUE unreachability.

In line 6. MME/AMF 106 sends an NIDD submit indication message toNEF/SCEF 102 indicating that a retransmission time has not elapsed. Inline 7 of the message flow diagram, NEF/SCEF 102 sends an NIDD submitrequest message on the T6a interface to MME/AMF 106 to initiateretransmission of the NIDD data to UE 108, which may be a narrowband IoTdevice. In this example, it is assumed that UE 108 is available.Accordingly, MME/AMF 106 initiates NAS data delivery to the UE. The NASdata delivery may include the service identifier so that only UEs thatare configured to provide the requested service respond. In line 8 ofthe message flow diagram, MME/AMF 106 sends an NIDD submit responsemessage on the T6a interface to NEF/SCEF 102. The NIDD submit responsemessage confirms successful service-specific data delivery to the UE. Inline 9 of the message flow diagram, NEF/SCEF 102 sends an MT NIDD submitresponse message to SCS/AS 100. The MT NIDD submit response messageconfirms successful completion of the service-specific group messagedelivery procedure.

FIG. 3 is a message flow diagram illustrating exemplary messagesexchanged for NAS data delivery to the UE in response to theservice-specific group message delivery procedure illustrated in FIG. 2.In FIG. 3, two alternate service-specific group message deliveryprocedures are illustrated. One service-specific group deliveryprocedure is initiated by NEF/SCEF 102. An alternate service-specificgroup message delivery procedure is initiated by short message servicecenter (SMS-SC) 110.

Referring to the message flow in FIG. 3, in step 1A, SMS-SC 110 sends aforward short message (FSM) message to MME/AMF 106 to initiate aservice-specific group message delivery procedure to UEs capable ofproviding the specific service. The FSM message includes theNB-IoT-service-info parameter, the IMSI, and the serving temporarymobile subscriber identifier (S-TMSI).

In the alternate delivery scenario, the service-specific group messageNIDD delivery is initiated by NEF/SCEF 102. As illustrated in step 1B,the alternate method is initiated by NEF/SCEF 102 sending an MT-NIDDmessage including NB-IoT-service-info parameter to MME/AMF 106 on theT6a interface. The MT-NIDD message may be generated by NEF/SCEF 102 inresponse to NEF/SCEF 102 receiving a message from SCS/AS 100 on the T8interface requesting service-specific group message delivery tonarrowband IoT devices.

Once MME/AMF 106 receives the message from either SMS-SC 110 or NEF/SCEF102, MME/AMF 106 in line 2 sends an S1 paging request message to eNB/gNB112. The S1-paging info message includes the IMSI, the S-TMSI, thetracking area identifiers (TAIs), and the NB-IoT-service-info parameter.

In response to receiving the S1-paging request message including theNB-IoT-service-info parameter, eNB/gNB 112 in line 3 sends apaging-NB-IoT message to UEs within the service area of eNB/gNB 112. Thepaging-NB-IoT message includes the IMSI or S-TMSI and theNB-IoT-service-info parameter.

UEs that receive the paging information including theNB-IoT-service-info parameter will wake up and perform the radiolatching procedure if the UE supports the specified service. If the UEdoes not support the specified service, the device will not perform thewake up and radio latching procedures.

In line 4 of the message flow diagram, it is assumed that UE 108receives the paging request message and is configured to provide theidentified service. Accordingly, UE 108 performs radio resource control(RRC) connection establishment procedures with eNB/gNB 112. In line 5 ofthe message flow diagram, eNB/gNB 112 sends an initial UE message thatin the illustrated example is a NAS control plane service request toMME/AMF 106.

In line 6, MME/AMF 106 initiates transmission of downlink data to theidentified UE. The downlink data is transmitted in a downlink S1 APmessage that carries a NAS data protocol data unit (PDU). In response toreceiving the NAS data PDU, eNB/gNB 112 sends an RRC downlink datamessage including the NAS PDU to UE 108. Once the UE confirms successfuldelivery, in line 7, eNB/gNB sends an indication of successful datadelivery to MME/AMF 106. In line 8, MME/AMF 106 sends a delivery supportmessage to either SMS-SC 110 or NEF/SCEF 102 indicating success orfailure of the delivery process. Thus, using the steps in FIG. 3,service-specific paging of UEs, such as NB-IoT devices is performed.

As stated above, one interface that requires modification to supportservice-specific group message delivery to NB-IoT devices is the T8interface between the SCS/AS and the NEF/SCEF. In particular, the submitNIDD request procedure must include parameters that identify the servicetype. Table 1 shown below illustrates the parameters that are includedin an NIDD request message.

TABLE 1 NIDD Request Message Parameters Attribute Name Data TypeCardinality externalId ExternalId 0 . . . 0 externalGroupIdExternalGroupId 0 . . . 1 msisdn Msisdn 0 . . . 1 self Link 0 . . . 1data Binary 1 reliableDataService Boolean 0 . . . 1 rdsPort RdsPort 0 .. . 1 maximumLatency DurationSec 0 . . . 1 priority Integer 0 . . . 1pdnEstablishmentOption PdnEstablishmentOptions 0 . . . 1 deliverystatusDeliveryStatus 0 . . . 1 requestedRetransmissionTime DateTime 0 . . . 1Nb-IoT-service-info String 0 . . . nIn Table 1, it can be seen that the NIDD request message includes theNB-IoT-service-info parameter which identifies the type of serviceprovided by the NB-IoT devices to which the message is directed.

Yet another interface that requires modification to supportservice-specific group message delivery is the T6a interface betweenNEF/SCEF 102 and MME/AMF 106. The message sent on this interface toprovide service-specific group message delivery is referred to as adiameter MT-data-request message. The following are exemplary parametersthat may be included in a Diameter-MT-data request message sent on theT6a interface for service-specific group message delivery.

-   <MT-Data-Request>=<DiameterHeader:8388734,REQ,PXY,16777346>    -   <Session-Id>    -   <User-Identifier>    -   <Bearer-Identifier>    -   [DRMP]    -   {Auth-Session-State}    -   {Origin-Host}    -   {Origin-Realm}    -   [Destination-Realm]    -   [OC-Supported-Features]    -   *[Supported-Features]    -   [Nb-lot-Service-Info]    -   [Non-IP-Data]    -   [SCEF-Wait-Time]    -   [Maximum-Retransmission-Time]    -   *[Proxy-Info]    -   *[Route-Record]    -   *[AVP]        In the list of parameters above, the MT-data request message        includes the NB-IoT-service-info parameter which identifies the        service provided by the NB-IoT devices to which the message is        directed.

On the S1 AP interface between MME/AMF 106 and eNB/gNB 112, the pagingmessage must also be modified to include the NB-IoT-service-infoparameter. Table 2 shown below illustrates exemplary parameters that maybe included in a paging message sent from MME/AMF 106 to eNB/gNB 112.

TABLE 2 Paging Message Parameters for Service-specific Group MessageDelivery to Narrowband IoT Devices IE Type and Assigned IE/Group NamePresence Range Reference Criticality Criticality Message M 9.2.1.1 YesIgnore Type UE Identity M 9.2.3.10 Yes Ignore Index Value UE Paging M9.2.3.13 Yes Ignore Identity Paging DRX O 9.2.2.16 Yes Ignore CN DomainM 9.2.3.22 Yes Ignore List of TAIs 1 Yes Ignore >TAI List Item 1 . . .EACH Ignore <max#ofTAIs> >>TAI M 9.2.3.16 — . . . NB-IoT Paging O9.2.1.115 Yes Ignore eDRX Information NB-IoT UE O 9.2.3.47 Yes IgnoreIdentity Index Value Enhanced O 9.2.2.123 Yes Ignore Coverage RestrictedCE-Mode-B O 9.2.1.129 Yes Ignore Restricted Nb-IoT-service- O 1 . . .String info <maxNoOf . . .>In Table 2, it can be seen that the paging message is modified toinclude the NB-IoT-service-info parameter as an optional parameter. TheNB-IoT-service-info parameter identifies the type of service provided bythe UEs to which the paging message is directed.

On the RRC interface between eNB/gNB 112 and UE 108, the narrowbandpaging message is also modified to include the NB-IoT-service-infoparameter. The message sent on the RRC interface is referred to as thepaging-NB message. The paging-NB message is used to notify one or moreUEs of a transmission. The paging-NB message is sent on the PCCH channelfrom the network to the UE. The following are parameters that may beincluded in the paging-NB message.

--ASN1START Paging-NB ::= SEQUENCE {PagingRecordList-r13 PagingRecordList-NB-r13OPTIONAL,--need onsystemInfoModification-r13 ENUMERATED {true} OPTIONAL,--need onsystemInfoModification-eDX-r13ENUMERATED OPTIONAL, --need on {true}nonCriticalExtension SEQUENCE { ) OPTIONAL } PagingRecordList-NB-r13 ::=SEQUENCE (size(1...maxPageRec) ) of PagingRecord-NB-r13PagingRecord-NB-r13 ::= SEQUENCE{ Ue-Identity-r13 PagingUE-Identity,Nb-IoT-service-info ... } --ASN1STOP

FIG. 4 is a block diagram of a network node that is capable ofperforming service-specific group message delivery to NB-IoT devices.The network node illustrated in FIG. 4 may be any of NEF/SCEF 102,SMS-SC 110, MME/AMF 106, or eNB/gNB 112. Referring to FIG. 4, networknode 102, 106, 110, or 112 includes at least one processor 114 and amemory 116. Network node 102, 106, 110, or 112 also includes aservice-specific group message delivery module 118 that receives thatinbound request for service-specific group message delivery on a firstinterface 120 and formulates and transmits an outbound message forservice-specific group message delivery on a second interface 122. Forexample, if the network node is NEF/SCEF 102, interface 120 may be theT8 interface, and interface 122 may be the T6a interface, such that thenetwork the node receives an inbound request on the T8 interface andformulates an outbound message for group message delivery to NB-IoTdevices on the T6a interface. In another example, if the network node isMME/AMF 106 interface 120 may be the T6a interface or the interface withSMS-SC 110, and the outbound interface may be the S1-AP interface. Ifthe network node is SMS-SC 110, interface 120 may be the interface withover which SMS-SC 110 communicates with SCS/AS 100, and interface 122may be the interface between SMS-SC 110 and MME/AMF 106. If the networknode is eNB/gNB 112, interface 120 may be the S1-AP interface, andinterface 122 may be the RRC interface.

FIG. 5 is a block diagram of UE 108 illustrating modifications forresponding to service-specific paging request messages. Referring toFIG. 5, UE 108 includes a processor 124 and a memory 126. UE 108 furtherincludes a service-specific wake up/response module 128.Service-specific wake up/response module 128 receives service-specificpaging messages on the RRC interface from eNB/gNB 112. Service-specificwake up/response module 128 decodes the service-specific paging messageto determine whether the service identified in the paging messagecorresponds to a service for which UE 108 is configured to support. Ifservice-specific wake up/response module 128 determines that the messageis directed a service for which UE 108 is configured to support,service-specific wake up/response module 128 may initiate a wake upprocedure to wake up UE 108 and cause UE 108 to respond to theservice-specific paging message. If service-specific wake up/responsemodule 128 determines that the service-specific paging message does notspecify a service for which UE 108 is configured, service-specific wakeup/response module 128 may ignore the message and refrain frominitiating the wake up procedure of UE 108.

FIG. 6 is a flow chart illustrating an exemplary process implemented bya network node, such as network node 102, 106, 110, or 112 illustratedin FIG. 4, for service-specific group message delivery to NB-IoTdevices. Referring to FIG. 6, in step 600, the network node receives ona first interface, a request for service-specific group message deliveryto one or more NB-IoT devices. For example, network node 102, 106, 110,or 112 may receive an inbound request for service-specific group messagedelivery. The message may arrive on the T8 interface if the network nodeis an SCEF or NEF, on the T6a interface if the network node is an MME orAMF, on the S1-AP interface if the network node is an eNB/gNB, or an SMSrelated interface if the network node is an SMS-SC.

In step 602, the sender is authenticated. The authentication step may beperformed if the network node is an NEF, SCEF, or SMS-C, where theoriginator, such as an SCS/AS, is authenticated. In step 604, if thesender is not authorized to send the message, control proceeds to step606 where a response is transmitted to the sender indicating thatauthorization to send the message has been refused.

In step 604, if it is determined that the sender is authorized to sendthe message, control proceeds to step 608 where a service-specific groupmessage delivery message is generated for transmission on a secondinterface to or towards NB-IoT devices. If the network node is an SCEFor NEF, the second interface may be the T6a interface, and the messagemay be an NIDD submit request message. If the network node is an MME orAMF, the second interface may be an S1-AP interface, and the messagetransmitted on the second interface may be an S1 paging message. If thenetwork node is an eNB or gNB, the second interface may be an RRCinterface, and the message may be a paging-NB-IoT message.

In step 610, the message is transmitted towards the NB-IoT devices onthe second interface. For example, the outbound message may betransmitted on the T6a, S1-AP or RRC interface depending on whether thenetwork node is an SCEF or NEF 102, an MME or AMF 106, an SMS-SC 110, oran eNB/gNB 112.

FIG. 7 is a flow chart illustrating an exemplary process that may beperformed by a UE in supporting service-specific group message delivery.Referring to FIG. 7, in step 700, the UE receives an RRC message forservice-specific group message delivery. For example, the RRC messagemay be a paging request that includes the NB-IoT-service-info parameter.

In step 702, the UE identifies the service type in the message.Identifying the service type may include implementing limited low powerdevice functionality sufficient to decode the NB-IoT-service-infoparameter.

In step 704, the UE determines whether the service type is a supportedservice type. Determining whether the service type identified in themessage is a supported service type may include comparing the servicetype in the message to store parameters that indicate the type ofservice that the IoT device provides. If the service type is not asupported service type, control proceeds to step 706 where the UE doesnot wake up or respond to the message. Thus, by recognizing that theservice type is not a service that the IoT device provides, the IoTdevice can conserve battery life and reduce signaling in the network. Ifthe identified service type is supported, control proceeds to step 708where the UE initiates the wake up procedure and responds to theservice-specific group message delivery message. The group messagedelivery message may be a message instructing all UEs in a service areathat support a give service type to wake up and provide sensor data toan IoT application server or service capability server. The IoT devicesthat support the identified service respond to the request, and the IoTdevice that do not support the identified service refrain from waking upor responding to the group message delivery message.

Thus, by providing for service-specific group message delivery to NB-IoTdevices, network resources are optimized by reducing the signaling loadon the network. Devices that are not configured to provide the serviceidentified in the group message delivery messages do not establish theradio channel with the eNB or gNB. As a result, signaling on the radioor wireless part of the network as well as the wired part of the networkis reduced. In addition, NB-IoT device battery utilization is improvedas devices avoid unnecessary wake up operations and do away withunnecessary establishment of radio channels.

The disclosure of each of the following references is incorporatedherein by reference in its entirety.

REFERENCES

-   1. 3GPP TS 23.682; 3rd Generation Partnership Project; Technical    Specification Group Radio Access Network; Evolved Universal    Terrestrial Radio Access (E-UTRAN); Architecture enhancements to    facilitate communications with packet data networks and    applications, (Release 16) V16.3.0 (2019-06).-   2. 3GPP TS 29.128; Mobility Management Entity (MME) and Serving GPRS    Support Node (SGSN) interfaces for interworking with packet data    networks and applications (Release 15) V15.5.0 (2019-03).-   3. 3GPP TS 36.331 3rd Generation Partnership Project; Technical    Specification Group Radio Access Network; Evolved Universal    Terrestrial Radio Access (E-UTRAN); Radio Resource Control (RRC);    Protocol specification (Release 15) V15.6.0 (2019-06).-   4. 3GPP TS 36.413; 3rd Generation Partnership Project; Technical    Specification Group Radio Access Network; Evolved Universal    Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol    (S1AP) (Release 15) V15.6.0 (2019-07).-   5. 3GPP TS 29.337; 3rd Generation Partnership Project; Technical    Specification Group Core Network and Terminals; Diameter-based T4    interface for communications with packet data networks and    applications (Release 15) V15.0.0 (2018-06).

It will be understood that various details of the subject matterdescribed herein may be changed without departing from the scope of thesubject matter described herein. Furthermore, the foregoing descriptionis for the purpose of illustration only, and not for the purpose oflimitation, as the subject matter described herein is defined by theclaims as set forth hereinafter.

What is claimed is:
 1. A method for service-specific group messagedelivery to narrowband Internet of things (IoT) devices, the methodcomprising; at a network node including at least one processor:receiving, on a first interface, a request for service-specific groupmessage delivery to narrowband IoT devices supporting a specifiedservice; generating, by the network node, a message for service-specificgroup message delivery for transmission on a second interface, themessage including a NB-IoT service information parameter for identifyinga narrowband IoT service provided by the narrowband IoT devicessupporting the specified service; and transmitting, from the networknode and on the second interface the message for service-specific groupmessage delivery to narrowband IoT devices.
 2. The method of claim 1wherein the network node comprises a service capability exposurefunction (SCEF), wherein the first interface comprises a T8 interface,and wherein the second interface comprises an S6a interface.
 3. Themethod of claim 1 wherein the network node comprises a network exposurefunction (NEF), wherein the first interface comprises a T8 interface,and wherein the second interface comprises an Nudm interface.
 4. Themethod of claim 1 wherein the network node comprises a short messageservice center (SMS-SC).
 5. The method of claim 1 wherein the networknode comprises a mobility management entity (MME), the first interfacecomprises an S6a interface and the second interface comprises an S1APinterface.
 6. The method of claim 1 wherein the network node comprisesan access management function (AMF), the first interface comprises anNudm interface and the second interface comprises an N2 interface. 7.The method of claim 1 wherein the network node comprises an evolved nodeB (eNB), the first interface comprises an S1AP interface, and the secondinterface comprises a radio resource control (RRC) interface.
 8. Themethod of claim 1 wherein the network node comprises a g-node B (gNB),the first interface comprises an N2 interface, and the second interfacecomprises a radio resource control (RRC) interface.
 9. The method ofclaim 8 wherein the message comprises a paging message.
 10. The methodof claim 1 comprising: receiving, by a narrowband IoT device, themessage for service-specific narrowband IoT group message delivery;determining, by the narrowband IoT device, whether the serviceidentified by the NB-IoT device service information parametercorresponds to a service provided by the narrowband IoT device; inresponse to determining that the service identified by the NB-IoT deviceservice information parameter corresponds to a service provided by thenarrowband Io device, initiating wake-up of the narrowband IoT device;and in response to determining that the service identified by the NB-IoTdevice service information parameter is not a service provided by thenarrowband IoT device, ignoring the message and refraining frominitiating wake up of the narrowband IoT device.
 11. A system forservice-specific group message delivery to narrowband Internet of things(IoT) devices, the system comprising; a network node including at leastone processor, the network node further including: a first interface forreceiving a request for service-specific group message delivery tonarrowband IoT devices supporting a specified service; aservice-specific group message narrowband IoT message generatorimplemented by the at least one processor for generating a message forservice-specific group message delivery to narrowband IoT devices, themessage including a NB-IoT service information parameter for identifyinga narrowband IoT service provided by the narrowband IoT devicessupporting the specified service; and a second interface fortransmitting the message for service-specific group message delivery tonarrowband IoT devices.
 12. The system of claim 11 wherein the networknode comprises a service capability exposure function (SCEF), whereinthe first interface comprises a T8 interface, and wherein the secondinterface comprises an S6a interface.
 13. The system of claim 11 whereinthe network node comprises a network exposure function (NEF), whereinthe first interface comprises a T8 interface, and wherein the secondinterface comprises an Nudm interface.
 14. The system of claim 11wherein the network node comprises a short message service center(SMS-SC).
 15. The system of claim 11 wherein the network node comprisesa mobility management entity (MME), the first interface comprises an S6ainterface and the second interface comprises an S1AP interface.
 16. Thesystem of claim 11 wherein the network node comprises an accessmanagement function (AMF), the first interface comprises an Nudminterface and the second interface comprises an N2 interface.
 17. Thesystem of claim 11 wherein the network node comprises an evolved node B,the first interface comprises an S1AP interface, and the secondinterface comprises a radio resource control (RRC) interface.
 18. Thesystem of claim 11 wherein the network node comprises a g-node B (gNB),the first interface comprises an N2 interface, and the second interfacecomprises a radio resource control (RRC) interface.
 19. The system ofclaim 11 comprising a narrowband IoT device for: receiving the messagefor service-specific narrowband Io message delivery; determining whetherthe service identified by the NB-IoT service information parametercorresponds to a service provided by the narrowband IoT device; inresponse to determining that the service identified by the NB-IoTservice information parameter corresponds to a service provided by thenarrowband IoT device, initiating wake-up of the narrowband IoT device;and in response to determining that the service identified by the NB-IoTservice information parameter is not a service provided by thenarrowband IoT device, ignoring the message and refraining frominitiating wake up of the narrowband IoT device.
 20. A non-transitorycomputer readable medium having stored thereon executable instructionsthat when executed by the processor of a computer control the computerto perform steps comprising: at a network node including at least oneprocessor: receiving, on a first interface, a request forservice-specific group message delivery to narrowband IoT devicessupporting a specified service; generating, by the network node, amessage for service-specific group message delivery for transmission ona second interface, the message including a NB-IoT service informationparameter for identifying a narrowband IoT service provided by thenarrowband IoT devices supporting the specified service; andtransmitting, from the network node and on the second interface themessage for service-specific group message delivery to narrowband IoTdevices.